System and method for providing transparency in delivering private network features

ABSTRACT

A method is provided that includes receiving a request from a communication device to establish a communication session with a mobile station, the mobile station being operable to roam between a private and a public network. The mobile station is signaled via a cellular data network that a call is being initiated for the mobile station. Signaling information may be exchanged with a voice gateway such that one or more voice circuits are established. A signaling pathway may be established between an Internet protocol private branch exchange (IP PBX) and the mobile station via the cellular data network. The establishment of the signaling pathway is substantially concurrent with the establishment of one or more of the voice circuits. One or more features associated with a private network are delivered to the mobile station during the communication session as an end user moves between the public and private networks.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.11/063,285 filed Feb. 21, 2005 now U.S. Pat. No. 7,068,622 and entitled“System and Method for Providing Transparency in Delivering PrivateNetwork Features” which is a continuation of U.S. application Ser. No.10/664,984 filed Sep. 15, 2003 and entitled “System and Method forProviding Transparency in Delivering Private Network Features”, now U.S.Pat. No. 6,888,808.

TECHNICAL FIELD OF THE INVENTION

This invention relates in general to the field of communications and,more particularly, to a system and method for providing transparency indelivering private network features.

BACKGROUND OF THE INVENTION

Networking architectures have grown increasingly complex incommunications environments. In addition, the augmentation of clients orend users wishing to communicate in various network environments hascaused many networking configurations and systems to respond by addingelements to accommodate the increase in networking traffic and thevarious enhancements that have been provided by numerous communicativeplatforms. In recent years, a series of protocols and architectures havebeen developed in order to accommodate a diverse group of end usershaving various needs. For example, certain protocols may be used in apublic environment, allowing an end user to conduct a communicationsession using a given communication device. Other protocols may providean end user with the ability to function adequately in a privatenetworking scenario, whereby a designated private network node may beaccessed to provide a platform that the end user may use to conduct acommunication session.

As both public and private network systems grow in size and insophistication, proper routing and efficient management of communicationsessions and data flows becomes even more critical. In cases whereprotocols are unable to accommodate a given service or feature, an enduser is precluded from enjoying the benefits of a given communicationarchitecture. Accordingly, the ability to provide an effective andmechanism to seamlessly process and direct communications for an enduser seeking to realize the benefits provided by multiple networkenvironments offers a significant challenge to network operators,component manufacturers, and system designers.

SUMMARY OF THE INVENTION

From the foregoing, it may be appreciated by those skilled in the artthat a need has arisen for an improved communications approach thatprovides for more appropriate protocol integration procedures inoffering optimal services and capabilities to an end user. In accordancewith one embodiment of the present invention, a system and a method fordelivering private network features in a public network are providedthat greatly reduce disadvantages and problems associated withconventional data management techniques.

According to one embodiment of the present invention, there is provideda method for providing transparency in delivering private networkfeatures that includes receiving a request from a communication deviceto establish a communication session with a mobile station, the mobilestation being operable to roam and handoff calls between a private and apublic network. The request is responded to by signaling the mobilestation via a cellular data network that a call is being initiated forthe mobile station. Signaling information may be exchanged with a voicegateway such that one or more voice circuits are established. Asignaling pathway may be established between an Internet protocolprivate branch exchange (IP PBX) and the mobile station via the cellulardata network. The establishment of the signaling pathway issubstantially concurrent with the establishment of one or more of thevoice circuits. One or more features associated with a private networkare delivered to the mobile station during the communication session asan end user moves between the public and private networks.

Certain embodiments of the present invention may provide a number oftechnical advantages. For example, according to one embodiment of thepresent invention a communications approach is provided that allows fora greater number of services and capabilities to be provided to an enduser in a seamless fashion. This is a result of the integration ofpublic and private networking features that may be realized at a singlelocation (e.g. a mobile station). Such an integration results in an enduser being able to benefit from the architectures of two communicationplatforms. Moreover, a given end user does not have to sacrificeprocessing time or inhibit his own versatility in being able to roam andenjoy the advantages of multiple networking systems. Furthermore, agiven call may originate in the private network or the public network:the call being originated or received by the mobile station beingimplicated in the communication session. Additionally, the architectureof the present invention may achieve a level of transparency for an enduser such that he/she is provided with maximum flexibility in utilizinga mobile station in multiple network environments.

Another technical advantage associated with one embodiment of thepresent invention is a result of the enhanced capabilities of the mobilestation. The mobile station is capable of providing services andfeatures of both private and public networks to end users in real-time.The mobile station may also consume minimal battery resources, whichextends the battery life for the mobile station. These performanceenhancements may be attained in a seamless fashion. Also, an end user ofa given communication device may have information displayed to him in amanner consistent with that of an enterprise network.

Yet another technical advantage associated with one embodiment of thepresent invention is the result of the configuration of thearchitecture, which provides for minimal overhead to be incurred inorder to enhance a given communication system. A communication systemcan be readily upgraded to accommodate the operations andfunctionalities provided by multiple network architectures. Thus, anexample implementation could be applicable to legacy systems where suchfeatures would be beneficial to a given group of end users. Moreover,numerous systems and architectures could be enhanced to accommodate sucha networking protocol without inhibiting the performance of either thepublic or the private network systems. Certain embodiments of thepresent invention may enjoy some, all, or none of these advantages.Other technical advantages may be readily apparent to one skilled in theart from the following figures, description, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present invention andfeatures and advantages thereof, reference is made to the followingdescription, taken in conjunction with the accompanying figures, whereinlike reference numerals represent like parts, in which:

FIG. 1 is a simplified block diagram of a communication system forproviding transparency in delivering private network features inaccordance with one embodiment of the present invention;

FIG. 2 is a simplified block diagram of an example architecture that maybe provided in a mobile station, which may be included in thecommunication system in accordance with one embodiment of the presentinvention; and

FIG. 3 is a flowchart illustrating a series of example steps associatedwith a method for providing transparency in delivering private networkfeatures.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS OF THE INVENTION

FIG. 1 is a simplified block diagram of a communication system 10 fordelivering private network features in providing transparency incommunications environment. Communication system 10 may include a mobilestation 12, a mobile switching center (MSC) 16, a cellular data network20, and a wireless local area network (WLAN) 22. Mobile station 12 isreplicated multiple times in FIG. 1 in order to illustrate an examplescenario in which roaming occurs between multiple network environments.As used herein in this document, the term “roaming” may indicate ascenario in which mobile station 12 moves from one network to anotherwhen it is in an idle state or during a call or a communication session.Additionally, the term “handoff” may be used to indicate a condition ofmobile station 12 moving from one network to another when there is anactive call/session.

Communication system 10 may also include an Internet protocol privatebranch exchange (IP PBX) 26, and/or a feature server 28, which is shownin a hatched box. Feature server 28 may be used to provide any one ormore of the functionalities of IP PBX 26, as described in more detailbelow. Communication system 10 may also include a voice over IP (VoIP)phone 30 and a voice gateway 32. Communication system 10 mayadditionally include a plurality of communication links 40 a-c, whichmay facilitate the delivery of voice data between VoIP phone 30, voicegateway 32, MSC 16, and mobile station 12. A public and a privatenetwork, as delineated by a dashed line in FIG. 1, may cooperate in thearchitecture of communication system 10 in order to deliver the benefitsof both networks to mobile station 12 as described more fully below.

FIG. 1 may be generally configured or arranged to represent a 2.5Gcommunication architecture applicable to a Global System for Mobile(GSM) environment in accordance with one embodiment of the presentinvention. However, the 2.5G architecture is offered for purposes ofexample only and may alternatively be substituted with any suitablenetworking protocol or arrangement that provides a communicativeplatform for communication system 10. For example, communication system10 may operate with any type of code-division multiple access (CDMA)architecture or cooperate with any version of a general packet radioservice (GPRS) tunneling protocol (GTP) that includes a platform forexecuting data management operations. This may be inclusive of firstgeneration, 2G, and 3G architectures that deliver a service or acapability to one or more clients or end users.

In accordance with the teachings of the present invention, mobilestation 12 may support multiple wireless communication protocols, suchas GSM, GPRS, CDMA, Bluetooth, 802.11, etc. An enterprise communicationsystem may deliver private network features to mobile station 12 whilemobile station 12 receives service within the enterprise system. Whenoutside the enterprise system, mobile station 12 receives wirelessservice from the public network, which continues to provide privatenetwork features via an enhanced signaling channel over a wirelesspublic data network. The enhanced channel is described in greater detailbelow. As mobile station 12 moves between private and public networksusing different wireless access technologies, not only does mobilestation 12 continue to receive the same private network PBX feature set,but private network PBX features may operate transparently as the usermoves between public and private networks.

Some example implementations that illustrate such a transparencycharacteristic may include calling numbers that are call forwarded andremain call forwarded as an end user moves between private and publicnetworks. In another call scenario, a call placed on hold in the privatenetwork using one wireless technology remains on hold and can be takenoff a hold status as the user transitions to the public network. In yetanother example scenario, a call “parked” in the public network over oneaccess technology can be picked up in the private network using adifferent access technology. Numerous other suitable private networkfeatures may be readily accommodated by communication system 10 anddelivered to an end user in transparent fashion.

In order to detail some of the transparency capabilities ofcommunication system 10, it is important to recognize the basis fromwhich such features operate. Underlying the aforementioned transparencycapabilities, communication system 10 is capable of providing a datacoordination scheme that allows for the ability of an enterprisecommunication system to deliver private network functionalities tomobile station 12, while it operates in a public wireless network.Mobile station 12 may use a public wireless protocol (e.g. GSM or CDMA)for voice transport and a public wireless data protocol such as GPRS,enhanced data GSM environment (EDGE), universal mobiletelecommunications service (UMTS), short message service (SMS),multi-media messaging (MMS), 1xRTT, 1xEV-DO, or 1XEV-DV, etc. for voicesignaling. This provides for a “traditional” voice connection over thewireless voice network and an enhanced signaling channel over a givenwireless data network.

The configuration of communication system 10 allows the enterprisesystem to establish a voice path between the private and public networkusing a voice network (e.g. via links 40 a-c). Communication system 10may also establish a separate signaling path (e.g. via cellular datanetwork 20). The separate signaling path may enable enhanced signalingto deliver private network information to mobile station 12 byestablishing a data connection from IP PBX 26 and mobile station 12 (viacellular data network 20). Thus, while in the public wireless network,mobile station 12 is able to receive private network PBX features (e.g.shared lines, call pickup, group pickup, directory functions, messagewaiting indicator, etc.) as if mobile station 12 were part of IP PBX 26in the private network. This allows the enterprise system to provide acommon set of private network features to mobile station 12 regardlessof whether mobile station 12 receives service from the private or publicnetwork.

Accordingly, communication system 10 offers a greater number ofservices, features, and capabilities to an end user of mobile station12. This is a result of the integration and delivery of public andprivate networking features. Additionally, a given end user does notsacrifice processing time or inhibit his own versatility in being ableto roam freely between various networks and enjoy the advantages of bothsystems. In addition, minimal overhead is incurred as a result of amodification to a given system in order to accommodate private andpublic network functions. Any communication architecture can be readilyupgraded to accommodate the features of both public and private systemsin a seamless fashion. Certain benefits of the architecture ofcommunication system 10 may be realized by mobile station 12 having anenhanced dual-mode functionality, or equally realized by mobile station12 in scenarios where no enhancements to its architecture are performed.The display of information at mobile station 12 (e.g. images,arrangements, etc.) can be provided to an end user in a manner that isconsistent with representations offered in the enterprise domain.

It is important to note that a given call may originate in the privatenetwork or the public network. In addition, the call may be originatedor received by mobile station 12, which is being implicated in thecommunication session. Calls may be properly anchored in the privatenetwork in order to achieve some of these operations.

In operation of an example overview embodiment used for purposes ofteaching only, a call may be initiated by VoIP telephone 30 to mobilestation 12. Signaling information may be exchanged over a link thatcouples IP PBX 26 and VoIP phone 30. IP PBX 26 is able to recognize thata call is being established that involves a given mobile unit (i.e.mobile station 12). Note that mobile station 12 may be equipped orenhanced such that it possesses dual-function capabilities.Alternatively, mobile station 12 may not be equipped for dual-functionoperations and yet still be fully operational in the context ofcommunication system 10. For example, such may be the case where theprivate and public networks are utilizing an 802.11 protocol.

Signaling may be initiated with mobile station 12 over cellular datanetwork 20 that a call is being constructed. This signaling function maybe part of IP PBX 26, or may reside in a separate feature server.Accordingly, signaling information (e.g. call-control information) maybe exchanged between IP PBX 26 and mobile station 12, whereby cellulardata network 20 can readily accommodate the communication session. IPPBX 26 may also send caller-identification information over cellulardata network 20 or, alternatively, IP PBX 26 may send any other suitableenterprise data sought to be passed through over the cellular datanetwork 20. As the signaling information is being exchanged between IPPBX 26 and mobile station 12 over cellular data network 20, IP PBX 26may also exchange signaling information with voice gateway 32. Thus,voice circuits (e.g. time-division multiplexing (TDM)) are establishedbetween voice gateway 32 and MSC 16 over communications link 40 b. Thisprovides a voice pathway for voice data to be exchanged between mobilestation 12 and VoIP phone 30.

Note that from a high-level perspective, the call illustrated throughvoice gateway 32 and to MSC 16 offers a media path, whereby signalingfeatures are provided via cellular data network 20. The private networkfeatures provided to an end user of mobile station 12 may include, butare not limited to, a ‘hold’ function, a conference call function, avoice mail function, a do not disturb function, a three-way callfunction, a message alert function, a call forwarding function, a callwaiting function, and a directory function. Note also that the voiceconnection may not necessarily need to be established until an end userdecides to execute some task or to initiate some operation. In addition,IP PBX 26 does not utilize any signaling information in the path ofvoice gateway 32. For example, if the ‘hold’ function is invoked, thenit may be fully supported via cellular data network 20.

Once the call-control path has been established or the call-controltransaction has been completed, IP PBX 26 may place a cellular call tomobile station 12 for the purpose of bringing up a media stream. Mobilestation 12 includes intelligence operable to react to call-controlinformation being communicated by cellular data network 20. Theintelligence is further capable of coordinating that transaction withthe cellular call that is coming in via one or more voice circuits. In ageneral sense, this allows mobile station 12 to realize the benefits ofoperating in both a private and a public network by effectively managingdata exchanges and signaling information associated with thecommunication session.

The cellular call may be presented to a given end user in a way that isconsistent with an enterprise call. This allows mobile station 12 toachieve the benefits of an enterprise (or private) network, whilemaintaining its existing capabilities in the public network environment.For example, once a call has been established a given end user of VoIPphone 30 can invoke a ‘hold’ feature. The initiation of the ‘hold’functionality may be communicated to IP PBX 26, which again may be ableto recognize that this communication session implicates mobile station12, which has enhanced capabilities to realize operational functions inboth private and public networks. IP PBX 26 may again exchangecall-control signaling with mobile station 12 over cellular data network20. Cellular data network 20 may signal (or “ping”) the user interfaceof mobile station 12 in order to place mobile station 12 into a ‘hold’mode. The ‘hold’ mode representation to an end user may reflect images,arrangements, and or protocols that are consistent with what isavailable in the enterprise network.

In operation of the reverse direction (again offered for purposes ofexample and teaching only), mobile station 12 may initiate a ‘hold’functionality by depressing a given key provided thereon. The requestmay propagate over cellular data network 20 to IP PBX 26. IP PBX 26 maythen invoke the ‘hold’ functionality in VoIP phone 30. IP PBX 26 maythen remain responsible for managing the media that is consistent withthe media handling capabilities as provided in the VoIP network in thisexample scenario.

With reference to a more detailed example embodiment that reflects thetransparency feature of communication system 10, communication system 10allows enterprise services to be delivered to mobile station 12 while itis in a cellular network. Additionally, communication system 10 allowssupport for such features when mobile station 12 moves into a voice-overIP network and, further, to support the features while engaged in thecall. For example, while operating in cellular data network 20, an enduser of mobile station 12 may place a call on ‘hold.’ While the call ison ‘hold’ mobile station 12 may roam into the enterprise or privatenetwork. Mobile station 12 may continue the call in the enterprisenetwork such that the call is seamlessly resumed.

IP PBX 26 may view a given call as a virtual call having multiple calllinks. Thus, when any PBX feature is invoked (e.g. call waiting, holdfunctions, resume etc.) it may be invoked on the virtual call andsubsequently the virtual call segment may be translated into an actualcall leg. Thus, if an end user is in cellular data network 20, then thevirtual call link can invoke the call-control transaction or protocol tosupport the enterprise feature. In cases where mobile station 12 is inthe enterprise network, IP PBX 26 may invoke the selected feature andsimply execute the designated operation.

One issue may arise as to how communication system 10 handles a scenarioin which call links exist in both public and private networks. In thecase of a seamless handoff, a ‘make before break’ operation may beperformed in order to ensure that a communication session is not lostduring a shared communication session involving two networkarchitectures. IP PBX 26 can readily accommodate such a scenario inallowing data of a given call to propagate via a virtual call link.Thus, when a new call link comes in, the call link is forced into thevirtual call link. For example, if an end user of mobile station 12 putssomeone on ‘hold’ in cellular data network 20, when mobile station 12moves back to the private network a voice-over IP call link isestablished. When the voice-over IP call link is received at IP PBX 26,it may recognize that this call link is the same as the cellular calllink. IP PBX 26 may also identify that the virtual call link is on‘hold’ so the voice-over IP call link is positioned in the ‘hold’ state.Then, with mobile station 12 in the enterprise network, an end user ofmobile station 12 can depress a resume key in order to continue with thecall in the enterprise network.

The virtual call link(s) may exist in IP PBX 26, whereby a call linkextends from mobile station 12 to IP PBX 26 in the cellular network (afirst link), from mobile station 12 to IP PBX 26 in an enterprisenetwork (a second link), and from voice-over IP phone 30 to IP PBX 26 (athird link). During a handoff, a switch may occur between the first andsecond call links. Thus, a function can be provided in IP PBX 26, whichmaintains the feature state consistent between the first and second calllinks, as movement occurs between them (i.e. as the call links come upand down). This allows mobile station 12 to continue to migrate to andfrom public and private networks in a seamless fashion between first andsecond call links while experiencing the features of both. IP PBX 26 isresponsible for forcing the call link into the state in which the callcurrently resides. Thus, in performing any feature in eitherenvironment, IP PBX 26 understands that when a second call leg is beingbrought up, the second call leg needs to be forced into the correctfeature state (e.g. ‘hold’).

Mobile station 12 is a wireless handset in accordance with a particularembodiment of the present invention, which includes intelligence that iscapable of facilitating private networking features in a public networkenvironment. This duality capability is described in greater detailbelow with reference to FIG. 2, which provides one example architectureof mobile station 12 that may be used to effectuate the operationsthereof. In other embodiments, mobile station 12 is a standard devicethat is capable of receiving the features and services available in botha public and a private network: without having any enhancements beingprovided to its internal structure. In certain embodiments, minorenhancements may be made to mobile station 12 in order to interfaceproperly with WLAN 22 applications.

Alternatively, mobile station 12 may generically represent an end user,a client, or a customer wishing to initiate a communication session incommunication system 10 via cellular data network 20 or IP PBX 26.Mobile station 12 may also be inclusive of other suitable devices usedto initiate a communication session, such as a computer, a personaldigital assistant (PDA), a laptop or an electronic notebook, atelephone, a mobile terminal, or any other device, component, element,or object capable of initiating voice or data exchanges withincommunication system 10. Mobile station 12 may also be inclusive of asuitable interface to the human user, such as a keypad, a microphone, adisplay, a keyboard, or other suitable terminal equipment. Mobilestation 12 may also be any device that seeks to initiate a communicationsession on behalf of another entity or element, such as a program, adatabase, or any other component, device, element, or object capable ofinitiating a voice or a data exchange within communication system 10.Data or information, as used herein in this document may refer to anytype of numeric, voice, video, audio-visual, or script data, or any typeof source or object code, or any other suitable information in anyappropriate format that may be communicated from one point to another.

MSC 16 is a network element that operates as an interface between mobilestation 12 and voice gateway 32 (i.e. via a public-switched telephonenetwork (PSTN)). MSC 16 may also be coupled to cellular data network 20.In alternative embodiments, MSC 16 may be replaced with any suitableaccess point operable to serve as a conduit for voice data, whichpropagates to or from mobile station 12. MSC 16 may also communicatewith various other pieces of networking equipment in order to facilitatecommunications involving mobile station 12. For example, MSC 16 maycommunicate with radio access network (RAN) equipment (potentiallyinclusive of a base station controller and a base transceiver station).

It is important to note that, based on any given communication scheme orarchitecture, any number of additional alternative components may alsobe used to facilitate communications involving mobile station 12.Elements such as a serving general packet radio service (GPRS) supportnode (SGSN), a data gateway, and a gateway GPRS support node (GGSN) mayreadily be used to facilitate the operations of mobile station 12. Otherapplications may include the use of a PSTN, a packet-switched datanetwork (PSDN), an access gateway, a WLAN, an IP network, a networkaccess server (NAS), a virtual private network (VPN) server, or anyother suitable networking equipment operable to facilitate theoperations of communication system 10 as described herein.

Mobile switching center 16 represents a location that generally housescommunication switches and computers and ensures that its cell sites ina given geographical area are connected. Cell sites refer generally tothe transmission and reception equipment or components, potentiallyincluding a number of suitable base stations that connect elements suchas mobile station 12 to a network. By controlling transmission power andradio frequencies, mobile switching center 16 may monitor the movementand the transfer of a wireless communications from one cell to anothercell and from one frequency or channel to another frequency or channel.Mobile switching center 16 may also generally handle connection,tracking, status, billing information, and other user information forwireless communications in a designated area. This may include, forexample, the fact that mobile station 12 is assigned certain wirelesscapabilities or use time: most likely based on a given fee scheduleassociate with a given mobile network (e.g. cellular data network 20).

Cellular data network 20 represents a series of points or nodes ofinterconnected communication paths for receiving and transmittingpackets of information that propagate to or from mobile station 12. Asubscription or an agreement may be provided by cellular data network 20to offer cellular service to an end user of mobile station 12. Cellulardata network 20 provide a pathway for exchanging signaling informationbetween IP PBX 26 and mobile station 12 such that enterprise featuresare delivered to mobile station 12 concurrently with features providedin a public network environment. Cellular data network 20 offers acommunicative interface between mobile station 12 and any suitablelocation within or external to communication system 10 and may berepresentative of a GPRS service provider or any suitable local areanetwork (LAN), WLAN, metropolitan area network (MAN), wide area network(WAN), VPN, or any other appropriate architecture or system thatfacilitates communications in a network environment. Cellular datanetwork 20 may implement a user datagram protocol (UDP)/internetprotocol (UDP/IP) communication language protocol in a particularembodiment of the present invention. Communication system 10 may utilizeany form of transmission control protocol (TCP)/IP, or alternativelyimplement any other suitable communications protocol for transmittingand receiving data or information within communication system 10.

WLAN 22 is a wireless protocol-networking node that allows mobilestation 12 to connect to a network through a wireless or a radioconnection. Such a protocol may be generally based on the IEEE 802.11standard or on any other suitable architecture that provides forwireless communications in a network environment. For example, WLAN 22may fully support technologies such as infrared, Bluetooth, and a numberof optical applications that may be used in the context of communicationsessions that implicate mobile station 12. WLAN 22 as referred to hereinin this document may also be representative of a ‘hot spot’ or a publicWLAN (PWLAN) where appropriate.

WLAN 22 may be coupled to mobile station 12 and cellular data network20, and may facilitate authentication procedures for an end user.Suitable encryption protocols may be included within a protocolassociated with WLAN 22 where appropriate and according to particularneeds. WLAN 22 may be inclusive of an access point and an access routeroperable to facilitate communication sessions, including authenticationprotocols in designated locations. The access router may aggregateaccess points within a corresponding hot spot. It may also provide aback haul from the public hot spot location to the corresponding corenetwork whether that core network is reflected by a broker's network oran operator's network. A single or a multiple operator broker networkmay be accommodated in accordance with the teachings of the presentinvention.

IP PBX 26 is a network component that resides in a private network andthat facilitates communications involving mobile station 12 regardlessof the network in which mobile station 12 operates. This functionprovides a communication path and an ability to establish a connectionwith mobile station 12 in order to properly accommodate the activitiesof an end user thereof. IP PBX 26 may also accommodate multiple calllinks as described above, in facilitating the operations that are beingdelivered to mobile station 12. In accordance with a particularembodiment of the present invention, IP PBX 26 includes softwareoperable to execute these operations. Alternatively, other elementscould be used or substituted within the architecture of IP PBX 26, whereappropriate, in order to address particular configuration needs. Forexample, any of the elements included within IP PBX 26 may be providedin any suitable hardware, processor, application program interface(API), application specific integrated circuit (ASIC), object, module,algorithm, or provided in any other suitable element based on particularcommunication needs. In certain applications or environments, any one ormore of the functionalities of IP PBX 26 may be provided externalthereto (e.g. within feature server 28). The elements included in IP PBX26 (or provided external thereto) may be reflective of accommodationsbeing made for a particular type of communications protocol or plan, adistributed architecture, or based on selected performance or serviceparameters.

In accordance with another embodiment of the present invention, featureserver 28 may be used to execute one or more of the functions providedby IP PBX 26. In still another embodiment, feature server 28 may beprovided within IP PBX 26 as a separate component or module, which isoperable to provide a communication path and an ability to establish aconnection with mobile station 12 in order to properly accommodate theactivities of an end user thereof. IP PBX 26 may simply invoke featureserver 28 in order to achieve dual-network benefits that are realized bymobile station 12. Thus, IP PBX 26 may cooperate with feature server 28,operate independent of feature server 28, or feature server 28 mayoperate without the assistance of IP PBX 26 in order to achieve thebenefits of private and public networking.

VoIP phone 30 is a communication device that exists in a private networkand that seeks to establish a communication session with mobile station12. In other embodiments, VoIP phone 30 may be replaced with any othersuitable communication device such as: a computer, a PDA, a laptop or anelectronic notebook, a telephone (potentially coupled to a videoconference bridge), a mobile station, or any other device, component,element, or object capable of initiating voice or data exchanges withincommunication system 10. The VoIP designation has been used for purposesof example only in providing one communication arrangement fordiscussion purposes. The VoIP protocol may be replaced with any suitablecommunication platform based on particular configuration needs. VoIPphone 30 may be replaced with any device, which may exist in the publicnetwork (e.g. a PSTN telephone, a cellular telephone, etc.).

Voice gateway 32 is a network node capable of facilitating voiceexchanges involving mobile station 12. Voice gateway 32 may receivesignaling information from IP PBX 26 after IP PBX 26 receives a requestto establish a call initiated by VoIP phone 30. Voice gateway 32 mayset-up a number of voice circuits (representative of a voice pathway)after receiving such signaling information: the voice pathway extendingbetween voice gateway 32 and MSC 16, via a given PSTN. Additionally, incertain scenarios, an integrated services digital network/integratedservices user part (ISDN/ISUP) link may be established between MSC 16and voice gateway 32. Alternatively, such a link may be replaced withany suitable connection or coupling that facilitates a data exchangethat may assist in any call involving mobile station 12. Voice gateway32 includes software that is operable to accommodate thedual-functionality being provided to mobile station 12. Alternatively,the software provided in voice gateway 32 may be replaced with anysuitable hardware, component, element, API, ASIC, module, or objectoperable to achieve the operations of voice gateway 32. In still otherembodiments, these elements may be provided external to voice gateway32.

FIG. 2 is a simplified block diagram of one example architectureassociated with mobile station 12. It is critical to note that thebenefits of private and public networking may be realized by a singlemobile station 12 that does not have any dual-mode capabilities or bymobile station 12 where it is only equipped with the ability to properlycooperate with WLAN 22. The description provided below is with referenceto a given mobile station having such capabilities, but such an internalstructure is not necessary. FIG. 2 simply offers one example embodimentof mobile station 12, which encompasses one or more dual-modefunctionalities. It is also important to note that the arrangement andconfiguration of the elements in FIG. 2 has been offered for purposes ofteaching only. Various items may be replaced, provided external tomobile station 12, or removed entirely from the architecture of mobilestation 12. Moreover the elements that may be included in mobile station12 may be reflective of accommodations being made for a particular typeof communications protocol or based on selected performance parameters.Other elements could be added to such an architecture where appropriatein order to address some of these concerns, which may be in accordancewith particular needs. It is critical to note the any of the elementsidentified below may be provided in any suitable software, hardware,processor, API, ASIC, object, module, algorithm, or provided in anyother suitable element where appropriate and based on particularcommunication protocols or architectures.

In general, mobile station 12 may support multiple differentcommunication modes, such as 802.11 and cellular protocols, and maysupport multiple different communication platforms, such as sessioninitiation protocol (SIP) and H.323 (as described more fully below). Forautomatic support of multiple protocols, mobile station 12 may executemultiple call-control modules: each supporting a separate protocol withan abstraction layer providing a wrapper around the call-controlmodules. During operation, the abstraction layer may pass receivedsignaling information to the appropriate call-control module. In orderto support multiple communication modes, mobile station 12 may integrateprotocol stacks, such as the 802.11 and cellular stacks for example,using a common interface. Thus, in one example scenario, an API mayprovide access to roaming and scanning functions of 802.11, while alsoproviding access to power management and other cellular roaming andcontrol functions.

Mobile station 12 may include an operations/administration (OA) andmanagement/policies (MP) element 60 that is coupled to a general module68, which includes an IP phone application 70, a signaling connectioncontrol part (SCCP) 72, a session initiation protocol 74, a man-machineinterface (MMI) 76 (e.g. a graphical user interface (GUI)), and anenterprise mobility protocol 78. A JAVA virtual machine (VM) 80 mayserve as a basis for these elements.

Mobile station 12 may also include a functions element 90 that includesa WLAN operations element 92 and an intelligence element 94. Functionselement 90 may exchange information with a virtual GSM driver 104 and avirtual WLAN driver 108, which are provided within a system serviceselement 100. System services element 100 may utilize a given operatingsystem 112, which may couple to an 802.11 shim 122 that is coupled to aTCP/IP stack 124. As illustrated in FIG. 2, a real-time transport/RTPcontrol protocol (RTCP) 128 and a discovery protocol 130 may also beprovided in mobile station 12.

Mobile station 12 offers flexibility in enabling the coordination ofdata communications from two different networks in a single unit. In ageneral sense, the call-control information may be abstracted in orderto provide a stack-switching capability (dynamically) in order toachieve the benefits of a private and a public network. Mobile station12 may include intelligence that identifies and understands both datastreams from both the private and public environment. Mobile station 12is further able to take information from IP PBX 26 and map it to thevoice information being communicated from the public network.

In operation, OA and MP element 60 provides provisioning operations formobile station 12. For example, for a given handset various securitycharacteristics and policies (e.g. numerous parameters associated with aVPN can be addressed via call processing), profile information (e.g.behavior of the phone inclusive of end user notification and tracking),and network parameters (e.g. potentially relating to speed, quality ofservice (QoS), etc.) may be assigned or provided to mobile station 12.Other policies to be accommodated by OA and MP element 60 may includeverification of a path based on an arbitrary rate plan. Such policiescould be dynamically controlled remotely or be locally controlled basedon particular needs. Additionally, a number of radio parameters may alsobe addressed by OA and MP element 60, including appropriate powerlevels, proper legal channels in which the end user can operate, optimaldata rates, etc. Roaming parameters may also be accommodated and relateto various networking thresholds (e.g. signal strength [comparing oneversus another] and channel utilization that examines the bandwidthbeing consumed).

IP phone application 70, SCCP 72, SIP 74, MMI 76, and enterprisemobility protocol 78 cooperate in order to provide a common approach toperforming a number of operations within mobile station 12 (e.g. placinga call on ‘hold,’ answering a call, etc.). The elements function toprovide a seamless transition to various functionalities offered by agiven network to mobile station 12. These elements provide a platformfrom which an end user can access both enterprise and public networkfunctions. Enterprise mobility protocol 78, which may be a seamlessserver-specific protocol, may be running as one of the contexts in JAVAVM 80. Enterprise mobility protocol 78 may communicate to a server thatis associated with IP PBX 26. In a general sense, enterprise mobilityprotocol 78 operates to announce that it may be entering the Wi-Finetwork and may also investigate what can be done for mobile station 12.

RTP/RTCP 128 is a basic streaming protocol that facilitates dataexchanges including mobile station 12. Discovery protocol 130 is alayer-two protocol that provides a broadcasting function for mobilestation 12 such that a network can recognize mobile station 12. Notethat mobile station 12 is capable of providing services and features ofboth private and public networks to end users in real-time. Mobilestation 12 also consumes minimal battery resources and can extendbattery life for mobile station 12.

TCP/IP stack 124 offers a standard base for mobile station 12 and may bepart of operating system 112. 802.11 shim 122 is a driver thatunderstands how to remove and add header information for incoming andoutgoing data. System services element 100 is an abstraction object thatruns on top of operating system 112. System services element 100 mayinclude any number of drivers based on particular communications needs.In the present example embodiment, system services element 100 includesvirtual WLAN driver 108 and virtual GSM driver 104.

Functions element 90 includes a number elements that offer theintelligence utilized to ensure proper execution of numerous tasks to beperformed by mobile station 12. For example, issues relating to powermanagement, Wi-Fi traffic, and cell environment may be addressed byintelligence element 94. Other issues such as roaming and scanning maybe addressed by WLAN element operations 92. Signal strength parametersand synchronization may also be addressed by functions element 90. Bothlayer-two and layer three roaming (e.g. identifying potential accesspoints and authentication schemes) may also be readily accommodated withthese elements.

Intelligence element 94 may also include objects to address Wi-Fiprotected access. Wi-Fi protected access activities may be coordinatedwith security policies already defined for a given profile of an enduser. Wireless multi-media extension (WME) operations may also beaccommodated by intelligence element 94. WME operations may be part ofQoS parameters and achieve certain power saving benefits. Numerous otherelements, software, APIS, ASICs, modules, hardware and components may beadded to mobile station 12 in order to achieve any desiredfunctionality. Such additions may account for protocols, security andbandwidth parameters, rate plan information, or any other attribute orcharacteristic associated with a communication session that implicatesmobile station 12. FIG. 2 offers just one of a myriad of potentialarrangements or configurations of mobile station 12 in order to achievethe dual-functionality in executing tasks and operations provided byboth a private and a public network.

FIG. 3 is a simplified flowchart illustrating a series of example stepsassociated with a method for providing transparency in deliveringprivate network features. The method may begin at step 100 where a callmay be initiated by VoIP telephone 30 to mobile station 12. At step 102,signaling information may be exchanged over a link that couples IP PBX26 and VoIP phone 30. IP PBX 26 includes intelligence capable ofrecognizing that a call is being set up that involves mobile station 12having enhanced capabilities such that it can successfully realize thebenefits of services and features provided in a public network and aprivate network.

At step 104, IP PBX 26 may signal mobile station 12, via cellular datanetwork 20, that a call is being established that implicates mobilestation 12. Accordingly, signaling information (e.g. call-controlinformation) may be exchanged between IP PBX 26 and mobile station 12via cellular data network 20 such that cellular data network 20 canreadily accommodate the communication session. IP PBX 26 may also sendcaller-identification information to mobile station 12 via cellular datanetwork 20 or, alternatively, IP PBX 26 may send any other suitableenterprise data sought to be passed through to cellular data network 20.Thus, IP PBX 26 establishes a data connection to mobile station 12 usingcellular data network 20.

As the signaling information is being exchanged between IP PBX 26 andmobile station 12, IP PBX 26 may also exchange signaling informationwith voice gateway 32 at step 106. Thus, voice circuits (i.e. a voicepathway for voice data to be exchanged between mobile station 12 and agiven communication device in the private network) are establishedbetween voice gateway 32 and MSC 16 over communications link 40 b.

After the call-control path has been established or the call-controltransaction has been completed, at step 108, IP PBX 26 may place acellular call to mobile station 12 for the purpose of bringing up amedia stream. Mobile station 12 includes intelligence operable to reactto call-control information being communicated by cellular data network20. The intelligence is further capable of coordinating that transactionwith the cellular call at step 110. In a general sense, this allowsmobile station 12 to realize the benefits of operating in both a privateand a public network by effectively managing data exchanges andsignaling information associated with the communication session.

The cellular call may be presented to a given end user in a way that isconsistent with an enterprise call at step 112. This achieves thebenefits of both public and private network environments. For example,once a call has been established a given end user of VoIP phone 30 caninvoke a conference call feature. The initiation of the conference callfunctionality may be communicated to IP PBX 26, which again may be ableto recognize that this communication session implicates mobile station12, having enhanced capabilities to realize operational functions inboth private and public networks. IP PBX 26 may again exchangecall-control signaling with mobile station 12 via cellular data network20. Cellular data network 20 may signal (or “ping”) the user interfaceof mobile station 12 in order to place mobile station 12 into aconference call mode. The conference call mode may be consistent withthe user interface that is available in the enterprise network.

At step 114, mobile station 12 may roam into an enterprise network. Forexample, while a call is on hold, mobile station 12 may roam into theprivate network. Mobile station 12 may continue the call in the privatenetwork in a seamless fashion. IP PBX 26 may view a given call as avirtual call having multiple call links. Accordingly, when any PBXfeature is invoked (e.g. a hold function) it may be invoked on thevirtual call and subsequently the virtual call segment may be translatedinto an actual call leg at step 116. Thus, if an end user is in cellulardata network 20, then the virtual call link can invoke the call controltransaction or protocol to support the enterprise feature. In caseswhere mobile station 12 is in the enterprise network, IP PBX 26 mayinvoke the selected feature and simply execute the designated operation.In cases involving seamless handoffs, a ‘make before break’ operationmay be executed to ensure that a communication session is not lost.These operations are used to achieve transparency and provide an enduser with maximum flexibility in operating mobile station 12.

Some of the steps illustrated in FIG. 3 may be changed or deleted whereappropriate and additional steps may also be added to the flowchart.These changes may be based on specific communication architectures orparticular interfacing arrangements and configurations of associatedelements and do not depart from the scope or the teachings of thepresent invention. It is important to recognize that FIG. 3 illustratesjust one of a myriad of potential implementations of communicationsystem 10.

Note that because of the considerable flexibility provided bycommunication system 10, a number of additional embodiments may be usedto achieve feature transparency. For example, the IP-PBX-feature serveranchor embodiment, as described herein, reflects the condition wherethere is a virtual call leg between mobile station 12 and feature server28, and a regular call leg between feature server 28 and VoIP phone 30.The virtual call leg comprises a call leg (VoIP over WLAN 22) over theprivate network, or a call leg over the public network (cellular CSVcall leg via MSC 16 and voice gateway 32). IP PBX 26 and mobile station12 may cooperate to ensure that the feature invoked on one call leg,comprising the virtual call leg, is consistent when a handoff istransferred to the complimentary call leg.

In another embodiment, additional operations may be performed via voicegateway 32, mobile station 12, and IP PBX 26 such that when mobilestation 12 is in the public network, a feature request to IP PBX 26 (orfeature server 28) over cellular data network 20 is tunneled/forwardedto voice gateway 32: allowing the feature to be invoked on the call legfrom voice gateway 32. When mobile station 12 is in the private network(VoIP WLAN), a feature request is not necessarily tunneled and isdirectly invoked on the call leg from mobile station 12.

In still another embodiment that provides for third party call control,IP PBX 26 (or feature server 28) may act as a third party controller,which on receiving the feature request, uses third party controls toinvoke the feature on the appropriate call leg. IP PBX 26 (or featureserver 28) is capable of maintaining consistency across the handoff inaccordance with the teachings of the present invention.

Although the present invention has been described in detail withreference to particular embodiments, it should be understood thatvarious other changes, substitutions, and alterations may be made heretowithout departing from the spirit and scope of the present invention.For example, although the present invention has been described withreference to certain steps and tasks to be performed to establish asignaling and a voice pathway, these steps may be altered considerably.Communication system 10 is malleable in that any number of processes orprocedures may be executed in order to achieve the dual-functionality asdescribed herein. The example scenarios and configurations have beenoffered for discussion purposes only and accordingly should be construedas such.

Moreover, although the present invention has been described withreference to a number of elements included within communication system10, these elements may be rearranged or positioned in any appropriatemanner to accommodate any suitable routing configurations. In addition,any of the elements of FIGS. 1 and 2 may be provided as separateexternal components to communication system 10 or to each other whereappropriate. For example, any of the enhanced functionalities of voicegateway 32, IP PBX 26, or mobile station 12 may be provided externalthereto in a single module or component that is operable to executetheir operations as identified herein. The present inventioncontemplates great flexibility in the arrangement of these elements aswell as their internal structure.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present invention encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims. In order to assist the UnitedStates Patent and Trademark Office (USPTO) and, additionally, anyreaders of any patent issued on this application in interpreting theclaims appended hereto, Applicant wishes to note that the Applicant: (a)does not intend any of the appended claims to invoke paragraph six (6)of 35 U.S.C. section 112 as it exists on the date of the filing hereofunless the words “means for” or “step for” are specifically used in theparticular claims; and (b) does not intend, by any statement in thespecification, to limit this invention in any way that is not otherwisereflected in the appended claims.

1. A method for enlisting one or more end users in a network environment in which delivery of one or more features occurs, comprising: enlisting one or more end users in a billing plan associated with network communications; generating a bill associated with one or more of the end users, the bill being based on the billing plan; and facilitating network communications for one or more of the end users in response to the end users being enlisted in the billing plan, whereby the network communications is facilitated by: a mobile station operable to conduct a communication session that involves a communication device, an Internet protocol (IP) private branch exchange (PBX) being operable to receive a request from a selected one of the communication device and the mobile station to establish the communication session, the IP PBX being operable to respond to the request by signaling to the mobile station that a call is being initiated that involves the mobile station, the IP PBX being operable to exchange signaling information with a voice gateway after receiving the request such that one or more voice circuits are established by the voice gateway in order to accommodate voice data that may propagate between the communication device and the mobile station, and wherein a signaling pathway is established between the IP PBX and the mobile station in response to the request such that one or more features associated with a private network are delivered to the mobile station during the communication session.
 2. The method of claim 1, wherein the mobile station includes a functions element operable to perform scanning and roaming operations for the mobile station.
 3. The method of claim 2, wherein the functions element is further operable to provide power management or wireless local area network (WLAN) operations for the mobile station.
 4. The method of claim 2, wherein the mobile station includes one or more virtual drivers operable to communicate with the functions element in order to facilitate a selected communications protocol being implemented in the communication session.
 5. The method of claim 1, wherein the IP PBX communicates call-identification information to the mobile station after receiving the request from the communication device.
 6. The method of claim 1, wherein signaling information associated with one or more functions performed at the mobile station and involving one or more of the features associated with the private network are received by the IP PBX and processed therein during the communication session.
 7. The method of claim 1, wherein the communication session is presented to an end user of the mobile station in a manner that is consistent with a display that may be offered in the private network.
 8. The method of claim 1, wherein the one or more of the features associated with the private network are a selected one of a group of elements consisting of: a) a ‘hold’ function; b) a conference call function; c) a voice mail function; d) a do not disturb function; e) a message alert function; f) a three-way call function; g) a call forwarding function; h) a call waiting function; and i) a directory function.
 9. The method of claim 1, wherein the mobile station includes an operations/administration (OA) and management/policies (MP) element operable to provide provisioning applications for the mobile station, the provisioning applications being associated with one or more policies provided to an end user of the mobile station.
 10. The method of claim 1, wherein the mobile station includes a general module that is operable to provide a communicative platform from which one or more of the features associated with the private network are delivered.
 11. The method of claim 1, wherein signaling information associated with one or more functions performed at the mobile station and involving one or more of the features associated with the private network are received by the IP PBX and processed therein during the communication session.
 12. The method of claim 1, wherein the IP PBX is operable to perform a make before break protocol as the mobile station moves between a public network and the private network such that the communication session is not lost.
 13. The method of claim 1, wherein the voice gateway is included in the signaling pathway such that signaling information associated with one or more functions performed at the mobile station and involving one or more of the features associated with the private network are received by the IP PBX and forwarded to the voice gateway.
 14. The method of claim 1, wherein the communication device is a voice over IP (VoIP) telephone.
 15. A method for enlisting one or more end users in a network environment in which delivery of one or more features occurs, comprising: enlisting one or more end users in a billing plan associated with network communications; generating a bill associated with one or more of the end users, the bill being based on the billing plan; and facilitating network communications for one or more of the end users in response to the end users being enlisted in the billing plan, whereby the network communications includes a protocol that comprises: communicating a request, from a selected one of a communication device and a mobile station, to establish a communication session that involves the mobile station, wherein signaling information is exchanged with a voice gateway after the request is received such that one or more voice circuits are established by the voice gateway in order to accommodate voice data that may propagate between the communication device and the mobile station; and establishing a signaling pathway between an Internet protocol (IP) private branch exchange (PBX) and the mobile station via the cellular data network in response to the request such that one or more features associated with a private network are delivered to the mobile station during the communication session.
 16. The method of claim 15, further comprising: exchanging signaling information between the IP PBX and the communication device after the request is received by the IP PBX.
 17. The method of claim 15, further comprising: performing a make before break protocol as the mobile station moves between a public network and the private network such that the communication session is not lost.
 18. The method of claim 15, further comprising: invoking one or more of the features associated with a private network at the IP PBX during the communication session.
 19. The method of claim 15, further comprising: presenting the communication session to an end user of the mobile station in a manner that is consistent with a display which may be offered in a private network.
 20. A method for enlisting one or more end users in a network environment in which delivery of one or more features occurs, comprising: enlisting one or more end users in a billing plan associated with network communications; generating a bill associated with one or more of the end users, the bill being based on the billing plan; and facilitating network communications for one or more of the end users in response to the end users being enlisted in the billing plan, whereby the network communications is facilitated by: a feature server operable to receive a request from a selected one of a communication device and a mobile station, which can conduct a communication session involving the communication device, the feature server being operable to respond to the request by signaling to the mobile station that a call is being initiated that involves the mobile station, the feature server being operable to exchange signaling information with a voice gateway after receiving the request such that one or more voice circuits are established by the voice gateway in order to accommodate voice data that may propagate between the communication device and the mobile station, and wherein a signaling pathway is established between the feature server and the mobile station in response to the request such that one or more features associated with the private network are delivered to the mobile station during the communication session.
 21. The method of claim 20, wherein the feature server is operable to communicate call-identification information to the mobile station after receiving the request from the communication device.
 22. The method of claim 20, wherein signaling information associated with one or more functions performed at the mobile station and involving one or more of the features associated with the private network are received by the feature server and processed therein during the communication session.
 23. The method of claim 20, wherein the feature server is operable to present the communication session to an end user of the mobile station in a manner that is consistent with a display that may be offered in the private network.
 24. The method of claim 20, wherein the one or more of the features associated with a private network are a selected one of a group of elements consisting of: a) a ‘hold’ function; b) a conference call function; c) a voice mail function; d) a do not disturb function; e) a message alert function; f) a three-way call function; g) a call forwarding function; h) a call waiting function; and i) a directory function.
 25. The method of claim 20, wherein the feature server is further operable to view the communication session as a virtual call having multiple call links such that when a selected one of the features is invoked, it is invoked on the virtual call and subsequently the virtual call can be translated into an actual call leg. 